-
Notifications
You must be signed in to change notification settings - Fork 411
Remove scary disconenct warnings on PeerManager new connection fns #1626
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove scary disconenct warnings on PeerManager new connection fns #1626
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1626 +/- ##
=======================================
Coverage 90.80% 90.81%
=======================================
Files 80 80
Lines 44654 44724 +70
Branches 44654 44724 +70
=======================================
+ Hits 40550 40618 +68
- Misses 4104 4106 +2
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK 561b4bc
Feel free to squash! |
In 4703d4e we changed PeerManager::socket_disconnected to no longer require that sockets which the PeerManager decided to disconnect not be disconnected. However, we forgot to remove the scary warnings on the `new_{inbound,outbound}_connection` functions which warned of the old behavior. We do so here.
Squashed without change. |
19b5a48
561b4bc
to
19b5a48
Compare
Ah, grr, totally forgot to point out the spelling mistake that persisted in the commit message after squashing.. |
Oops, sorry lol. Oh well. |
In 4703d4e we changed
PeerManager::socket_disconnected to no longer require that sockets
which the PeerManager decided to disconnect not be disconnected.
However, we forgot to remove the scary warnings on the
new_{inbound,outbound}_connection
functions which warned of theold behavior.
We do so here.